bpo-31227: regrtest reseeds RNG before each test#3059
Closed
vstinner wants to merge 4 commits into
Closed
Conversation
regrtest now reseeds the random RNG before each test file. Use also more entropy for the seed: 2**32 (32 bits) rather than 10_000_000 (24 bits).
vstinner
changed the title
Member
Author
|
I added a test to make sure that the behaviour is the same when tests are run in parallel. |
Member
Author
|
I didn't get a strong +1 on the issue and I'm not convinced myself by my approach. Moreover, Refleaks buildbots now seem to be reliable thanks to other fixes. For all these reasons, I close the PR. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
regrtest now reseeds the random RNG before each test file.
Use also more entropy for the seed: 2**32 (32 bits) rather than
10_000_000 (24 bits).
https://bugs.python.org/issue31227